Apparatus for temporal scheduling of a load to be transported

ABSTRACT

An apparatus is provided for improved processing of instructions to provide temporal selection to a client when scheduling a load to be transported for a prospective transportation industry customer. The apparatus includes a processor and a non-transitory machine readable memory. The processor is designed to process instructions to provide date and time selection to a client from a server to enable temporal scheduling of a load to be transported for a prospective transportation industry customer. The non-transitory machine readable memory at a host server has stored therein computer instructions programmed to cause the processor to store and access user information and instructions, and to present, enable, receive, store and associate date ranges, time ranges and waypoints for a load and cargo delivery destination. A method is also provided.

RELATED PATENT DATA

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 61/946,610, filed Feb. 28, 2014, entitled, “System and Methodfor Time Managing Loads in the Transport of Goods”, the entirety ofwhich is hereby incorporated by reference.

TECHNICAL FIELD

This disclosure pertains to business-to-business (B2B) transactions.More particularly, this disclosure relates to apparatus and methods formanaging the transportation of freight.

BACKGROUND

Techniques are known for scheduling loads for delivery on behalf of acustomer using a carrier. Such scheduling typically involves collatingof multiple independent communications from one or more of phone calls,emails, and facsimiles from one or more customer and/or carriers.Logistics capabilities have yet to minimize efforts in intermediatingload delivery for customers by carriers. Therefore, there exists a needto improve temporal selection of a load to be delivered and a load to bescheduled for delivery by a carrier that is to be transported for aprospective transportation industry customer.

SUMMARY OF THE INVENTION

A system and method are provided for managing the transportation offreight between shippers, brokers, and carriers. Functional interactionbetween the shippers, brokers, and carriers is provided in a differentmanner than is currently implemented in a “bricks & mortar” businessmodel.

According to one aspect, a computer-implemented system of providing dateand time selection to a client from a server is provided to enabletemporal scheduling of a load to be transported for a prospectivetransportation industry customer. The system includes user informationand instructions and a computer processor. The user information andinstructions are stored in a computer memory at a host server. Thecomputer processor accesses the memory at a host server to retrieve theuser information and instructions and executes the instructions toperform steps including: presenting from the server to the client at auser interface one or more of a selectable date range and a time rangefor which the user provides a temporal-based requirement for picking upa customer load; enabling selection of one or more of a date range and atime range at a user interface of the client; receiving a selected oneor more of the date range and the time range at the server from a userat the client; storing the received information into the database;associating the stored temporal data with a waypoint indicative of acargo delivery destination desired by a customer; associating the storedwaypoint to a load; and associating the attached load to the customer.

According to another aspect, a method is provided for enabling date andtime selection from a client through a server to enable temporalscheduling of a load to be transported for a prospective transportationindustry customer.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the disclosure are described below withreference to the following accompanying drawings.

FIG. 1 is a block diagram of the central processing system and networkused to carry out temporal selection of a load to be delivered and aload to be scheduled for delivery by a carrier that is to be transportedfor a prospective transportation industry customer according to anexemplary embodiment.

FIG. 2 illustrates a flowchart for implementing user authentication andpermissions to access through one or more interfaces the features andfunctionality of FIG. 1 in accordance with an exemplary embodiment.

FIG. 3 illustrates a flowchart for displaying load data to users andclients and for selecting and transmitting temporal data requirementsfor shipping the load.

FIGS. 4A and 4B together illustrate a flowchart for a customer selectingcarrier bids, approving carrier rates, accepting carrier bids, andstoring multiple customer approved bids on a load.

FIG. 5 illustrates a screen shot of a web page for a simple request fora broker for posting loads and identifying shippers and receivers of atype that would be displayed on the screen of one of the computersconnected for communication with the processing circuitry of the serverfor the system of FIG. 1.

FIG. 6 illustrates a screen shot of a web page for a date/time/selectionmenu that pops up when a user selects a “Date & Time” field in one ofthe shipper and received fields of FIG. 5.

FIG. 7 illustrates a screen shot of a web page showing a user “mousingover” a selected date range field prior to selecting a time range.

FIG. 8 illustrates a screen shot of a web page showing a selectedtemporal range achieved in FIG. 7.

FIG. 9 illustrates a screen shot of a web page showing selection of areceiver “Set Date & Time” field.

FIG. 10 illustrates a screen shot of a web page showing a selected atemporal range for the pop-up menu of FIG. 6.

FIG. 11 illustrates a screen shot of a web page for realizing thetemporal range selected in FIG. 10.

FIG. 12 illustrates a screen shot of a user login page.

FIG. 13 illustrates a screen shot of a customer dashboard.

FIG. 14 illustrates a screen shot showing customer load details.

FIG. 15 illustrates a screen shot showing a customer new load.

FIG. 16 illustrates load details including a new load with a temporalrange selection.

FIG. 17 illustrates a flowchart depicting account manager loadinteraction flow and privileges in accordance with an exemplaryembodiment.

FIGS. 18A and 18B together illustrate a flowchart depicting a system forrating carriers having checks and balances in accordance with anexemplary embodiment.

FIGS. 19A and 19B together illustrate a flowchart depicting logic behindselection of a temporal range in accordance with an exemplaryembodiment.

FIG. 20 illustrates a screen shot for a carrier profile to accessthrough one or more interfaces the features and functionality of FIG. 1in accordance with an exemplary embodiment.

FIG. 21 illustrates a screen shot depicting a load profile with quotesattached to a load with ratings.

FIG. 22 illustrates a screen shot depicting a menu for interacting witha carrier rate on a load menu.

FIG. 23 illustrates a screen shot depicting a customer profile.

FIG. 24 illustrates a screen shot depicting a brand new load.

FIG. 25 illustrates a screen shot depicting the selection of equipmentfor the new load depicted in FIG. 24.

FIG. 26 illustrates a screen shot depicting a new load and adding a lineitem to a customer's invoice.

FIG. 27 illustrates a screen shot depicting realization of the line itemadded to the customer's invoice of FIG. 26.

FIG. 28 illustrates a screen shot depicting the ability to add a shipperand a receiver for a designated city and state.

FIG. 29 illustrates a screen shot depicting a pop-up menu whileselecting a temporal date range.

FIG. 30 illustrates a screen shot depicting the pop-up menu of FIG. 30while selecting a temporal time range.

FIG. 31 illustrates a screen shot depicting the pop-up menu of FIGS. 30and 31 while selecting a temporal “after” time range.

FIG. 32 illustrates a screen shot depicting a realized selected temporalrange implemented via actions depicted in FIGS. 29-31.

FIG. 33 illustrates a screen shot depicting automatically convertedunits of weight for a specific cargo over that entered in the screenshot of FIG. 32.

FIG. 34 illustrates a screen shot depicting a load status change “PUT ONHOLD” resulting from selection of a “POST TO LOAD BOARDS” field in FIG.35.

FIG. 35 illustrates a screen shot depicting the adding of a carrierquote where permissions change the rate and “XYZ TRUCKING” is added.

FIG. 36 illustrates a screen shot depicting the addition of a secondcarrier quote to provide for multiple quotes.

FIG. 37 illustrates a screen shot depicting a carrier quote menu.

FIG. 38 illustrates a screen shot depicting a pop-up menu for addingcarrier quote equipment.

FIG. 39 illustrates a screen shot depicting realized changes of carrierquote equipment type from FIG. 38 to FIG. 39.

FIG. 40 illustrates a screen shot depicting the addition of a note to acarrier.

FIG. 41 illustrates a screen shot depicting realization of the addednote input in FIG. 40.

FIG. 42 illustrates a screen shot depicting realizing equipment changesfor the listed carrier with the added note and approval of “XYZTRUCKING”.

FIG. 43 illustrates a screen shot depicting realized changes forapproved carrier “XYZ TRUCKING”.

FIG. 44 illustrates a screen shot depicting creation of carrier ratepaperwork.

FIG. 45 illustrates a screen shot depicting a pop-up screen thatprovides a secondary check to a user indicating that this operation isdesired by the user.

FIG. 46 illustrates a screen shot depicting realization of carrier rateconfirmation paperwork.

FIG. 47 illustrates a screen shot depicting realization of customer rateconfirmation paperwork.

FIG. 48 illustrates a screen shot depicting selection of change of loadstatus to “IN TRANSIT”.

FIG. 49 illustrates a screen shot depicting realization of selection ofthe changed load status in FIG. 48.

FIG. 50 illustrates a screen shot depicting added notes to a load withcarrier permissions to view.

FIG. 51 illustrates a screen shot depicting that selection is being madefor making it visible to a customer.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

This disclosure is submitted in furtherance of the constitutionalpurposes of the U.S. Patent Laws “to promote the progress of science anduseful arts” (Article 1, Section 8).

FIG. 1 shows a platform or system 10 used to carry out temporalselection of a load to be delivered and a load to be scheduled fordelivery by a carrier that is to be transported for a prospectivetransportation industry customer according to an exemplary embodiment.The system 10 includes a network, such as the Internet 12, a server 14,and terminals, or clients 16, 18, 20, 22, 24 and 26. Server 14 includesone or more processor having processing circuitry 28 and data storage 30having memory 32 communicating with the processing circuitry. Memory 32includes, or defines one or more databases 33 configurable to storedata. Server 14 includes one or more network adapters 15 that enablescommunication with a network, such as the Internet 12. Clients 16 and 18comprise shipper terminals used by Shipper A and Shipper B,respectively. Clients 20 and 22 comprise broker terminals used by BrokerA and Broker B, respectively. Clients 24 and 26 comprise carrierterminals used by Carrier A and Carrier B, respectively. Each client isfurther understood to include a wired or wireless communications device,memory, one or more processors having processing circuitry, aninput/output device with a display driver for connecting the client toan input/output (I/O) device, such as a display, a keyboard, and amouse. The display driver transforms digital data into visual imagesperceptible by a user at the client capable of generating screen imagesvisible on the display. In several forms, client is a personal computer,a laptop, a tablet, or a smart phone.

As shown in FIG. 1, it is understood that one or more input modules canbe generated by server 14. Such modules are each configured to cause agraphical user interface to be rendered on a user's client machine, orcomputer to enable a user to input data relating to selection,scheduling, and delivery of a load (freight). Such interface rendersfeatures provided on the screen shots provided herein. Similarly, outputmodules are configured to display results of the data that is input by auser.

FIG. 2 illustrates a flowchart for implementing user authentication andpermissions to access through one or more interfaces the features andfunctionality of FIG. 1 in accordance with an exemplary embodiment. Withreference to FIG. 2, a flow of logic that is executed in variousembodiments, when implementing user authentication and permissions isillustrated. The process can start at step 200. After start 200, theprocess proceeds to step 201 where a user public page is presented atone or more clients where a user can input their credentials. After step201, the process proceeds to step 202 where the input user credentialsare sent via HyperText Transfer Protocol Secure (HTTPS) to server 14 (ofFIG. 1). After performing step 202, the process proceeds to step 203where a user is authenticated (with a userid and a password). If theuser is authenticated, then the process proceeds to step 204. If theuser is not authenticated, the process proceeds to step 201. In step204, the process compares user type and user group to determine whichcategory a user is identified with including a customer interface atstep 205, a carrier interface at step 206 and a “Type N” interface atstep 207. Once a user has been identified and assigned to a usercategory, the process proceeds to step 208. In step 208, the processprepares permissions and views based on a user sub-type, such as“broker”, “customer”, and “account manager”. After performing step 208,the process proceeds to step 209. In step 209, a completely functionalinterface is displayed to the authenticated (identified) andpermissioned user.

FIG. 3 illustrates a flowchart for displaying load data to users andclients and for selecting and transmitting temporal data requirementsfor shipping the load. With reference to FIG. 3, a flow of logic that isexecuted in various embodiments, when implementing the display of loaddata to users and clients and for selecting and transmitting temporaldata requirements (date range and time range) is illustrated. Theprocess can start at step 300. In step 300, a complete interface (withcomplete interface functionality) is displayed to a user at a specificclient. After performing step 300, the process proceeds to either step301 or step 302. In step 301, a user searches for a load, then proceedsto step 302. In step 302, a user selects a load default from a list.After performing step 302, the process proceeds to step 303 where aclient sends a request to server 14 (of FIG. 1). After performing step303, the process proceeds to step 304 where the server returns loadinformation to the client. After performing step 304, the processproceeds to step 305 where the client displays the load data. Afterperforming step 305, the process proceeds to step 306 where the userselects a waypoint temporal data input field (such as a range of datesand/or a range of times) for which a designated load is to bepicked-up/delivered to a desired destination. After performing step 306,the process proceeds to step 307 where the client displays a userinterface with a temporal data selector (a date range and/or a timerange). After performing step 308, the process proceeds to step 308where the user inputs required temporal data (date range and/or timerange). After performing step 308, the process proceeds to step 309where the client transmits the selected temporal data to the server 14(of FIG. 1). After performing step 309, the process proceeds to step 310where the server stores the selected temporal data to an associatedwaypoint (a coordinate or location on the freight delivery path).

As detailed in FIG. 3, temporal date/time range storage is provided forlogistics purposes. For each “waypoint” in a freight delivery (begin,midpoint, end, etc.) on a load to be transported, there exist pick-upand drop-off dates and/or times. There exist five different options tofill the temporal field with data including: “Between”; “Before”;“After”; “At”; and “N/A” (not available). These dates and times are thenparsed in different ways in order to distribute them to industrystandard load boards, such as GetLoaded, Dat360, and Internet Truckstop.Such distribution is an optional feature.

As used herein, the terms “carrier rate”, “carrier bid”, and “carrierquote” are used interchangeably until a carrier is fully signed on for aload, after which the designation becomes “carrier-on-board”.

FIGS. 4A and 4B together illustrate a flowchart for a customer selectingcarrier bids, approving carrier rates, accepting carrier bids, andstoring multiple customer approved bids on a load. With reference toFIGS. 4A and 4B, a flow of logic that is executed in variousembodiments, when implementing the display of load data to users andclients and for selecting and transmitting temporal data requirements(date range and time range) is illustrated. The process can start atstep 400. After step 400, the process proceeds either to step 401 orstep 402. In step 401, a customer searches for a load using a specificclient. After performing step 401, the process proceeds to step 402where a user selects a load default from a list of loads. Afterperforming step 402, the process proceeds to step 403 where the clientsends a request to the server 14 (of FIG. 1). After step 403, theprocess proceeds to step 404 where the server returns load informationto the client. After step 404, the process proceeds to step 405 wherethe clients displays load data. After step 405, a query is made at step406 as to whether a specific account type and load status is enabled toview bids. If not, the process proceeds to step 407 where a load isdisplayed without any bids. If enabled, the process proceeds to step 408where all current carrier bids and/or quotes are displayed at a client(including multiple bids displayed concurrently). After performing step408, the process proceeds to step 409 where a customer selects a carrierbid from a list of currently submitted bids. After performing step 409,the process proceeds to step 410 where a multi-variate query is madeabout four responses that can be taken after carrier bid information isdisplayed at a client. At step 410, a user is presented with fourchoices. A first choice is triggered by a user selecting an approvedbutton (on a user interface of the client) that causes the process toproceed to step 411. A second choice is triggered by a user selecting adecline button (on a user interface of the client) that causes theprocess to proceed to step 422. A third choice is triggered by a userselecting an add note/comment via a text box and submitting it thatcauses the process to proceed to step 423. A fourth choice is triggeredby a user selecting a click on name button (listing a static profile fora carrier) which proceeds to step 424. After performing step 424, theuser then clicks on a back button to return the process back to step410. In step 411, the customer approves the provided carrier rate. Instep 422, a customer denies a carrier rate and the process proceeds tostep 414. After a customer denies a rate at step 422, the system changesthe status of the bid relative to the customer's interface. In step 423,a customer sends the carrier a message and the process proceeds to step414. After step 411, the process proceeds to step 412 where the clientsends approval to the server. After step 412, the process proceeds tostep 413 where the server marks the bid as approved. After step 414, theprocess proceeds to step 414 where a notification is dispatched to thecarrier and/or account representative. After step 414, the processeither proceeds back to step 409 or forward to step 415. In step 415,the server stores multiple customer approved bids on a load. After step415, the process proceeds to step 416 where individual carriers arenotified of bid approval and asked to confirm their availability todeliver a specific load. After performing step 416, the process proceedsto step 417 where the carrier responds by confirming their availability(to the server). After step 417, the process proceeds to step 418 wherethe server sets the first carrier to respond to the load. After step418, the process proceeds to step 419 where the server updates the loadpast the bidding status. After step 419, the process proceeds to step420 where the server sends out notification to all non-conformingcarriers that the specific load is closed (and not open for bidacceptance). More particularly, the term “closed” is applied to loads todenote that the load is delivered. After performing step 420, theprocess proceeds to step 421 where the server sends out notification tothe customer that a carrier has been set (or assigned) to carry theirparticularly load. At this point, the process terminates.

As detailed in FIG. 4, a multiple quote and simultaneous approvalprocess is disclosed. When a customer is logged in and look at quotesthat have been submitted by various carriers, they are enabled with theability to approve multiple carriers at the same time. Once thishappens, an automated notification goes out to all carriers approved,requesting confirmation of their availability. The first carrier thatlogs into the website and provides an availability verification tocomplete the load in question is then changed to become the provider.The remaining carriers are then automatically notified that they weretoo slow to become the provider, and the load is no longer available.

FIG. 5 illustrates a screen shot of a web page for a simple request fora broker for posting loads and identifying shippers and receivers of atype that would be displayed on the screen of one of the computersconnected for communication with the processing circuitry of the serverfor the system of FIG. 1. More particularly, a cursor 501 is positionedover “Set Date & Time” field 502 which provides a selectable navigationlink that opens up a temporal range pop-up window 601 depicted in FIG.6, below.

FIG. 6 illustrates a screen shot of a web page for a date/time/selectionmenu that pops up when a user selects a “Set Date & Time” field 502 inone of the shipper and received fields of FIG. 5. More particularly,pop-up menu 601 includes a temporal date range selection menu item 602and a corresponding temporal time range selection menu 603 via which auser can select a temporal range (time and/or date) using a singleclick/drag of a mouse and cursor over the calendar displayed inselection menu 602. A temporal date range is shown as selection field606. A selectable date identifier “At” 607 is selected in menu 601corresponding with a single selected date shown in a date field 605shown directly below. Another date indicated by menu item 604representing Jan. 22, 2104 shows the current date via a round circle,whereas the “At” selected date will show up on the calendar via arectangular surround feature corresponding with the date shown in datefield 605. Other date identifiers of menu 601 for selecting a date, ordate range that are selectable include, “Between”, “Before”, “After”,and “Don't Set”.

FIG. 7 illustrates a screen shot of a web page showing a user“mousing-over” and selecting date range field 606 (with a cursor) oftemporal date range selection menu 602 separate from selecting a timerange 609 via a “between” time field selection 608 of a temporal daterange selection menu 602. Furthermore, a temporal time range selectionmenu 603 is also provided for selecting and inputting dates forrespective date ranges.

FIG. 8 illustrates a screen shot of a web page showing a selectedtemporal range achieved in FIG. 7. More particularly, a cursor 801 ispositioned over a selectable navigation date range link 802 that opensup the temporal range pop-up window 601 depicted in FIG. 7, above.

FIG. 9 illustrates a screen shot of a web page showing selection of areceiver “Set Date & Time” field 902 by “mousing-over” a cursor 901 andselecting field 902. More particularly, cursor p01 is positioned over“Set Date & Time” 902 which provides a selectable navigation link thatopens up a temporal range pop-up window 601 depicted in FIG. 10, below.

FIG. 10 illustrates a screen shot of a web page showing a selectedtemporal range for the pop-up menu of FIG. 6 that pops up when a userselects a “Set Date & Time” field 902 in the receiver field of FIG. 9.More particularly, pop-up menu 601 includes a temporal date rangeselection menu item 602 and a corresponding temporal time rangeselection menu 603 via which a user can select a temporal range (timeand/or date) using a single click/drag of a mouse and cursor over thecalendar displayed in selection menu 602. A temporal date range is shownby selection field 1006. A date identifier “Between” 1008 is selected inmenu 601 corresponding with a range of dates shown in a date field 1005shown directly adjacent. Another date indicated representing Jan. 22,2014 shows the current date via a round circle. Other date identifiersof menu 601 for selecting a date, or date range that are selectableinclude, “At”, “Before”, “After”, and “Don't Set”.

FIG. 11 illustrates a screen shot of a web page for realizing thetemporal range selected in FIG. 10. More particularly, a temporal dateand time range 1102 and 1104 is provided for the shipper and thereceiver, respectively.

FIG. 12 illustrates a screen shot of a user login page having a loginmenu 1201 for receiving user login information including email adrees,and password information that enables permissioned login to features ofthe website portal described variously in FIGS. 1-52.

FIG. 13 illustrates a screen shot of a customer dashboard illustrating acustomer's specific freight requests, or loads that a particularcustomer has pending. Loads are shown in various stages in any scenario.One exemplary shown freight request for shipping a freight load fromSeattle, Wash. to Key West, Fla. is shown in field 1302 when a “MyFreight” menu item 1304 is selected with a mouse (or input device) viacursor 1301. A draft load request 1306 is shown for a load that thecustomer is still working on, but is not yet fully filled in andsubmitted. In contrast, field 1302 shows a customer name 1312, anin-house tracking number 1318 for identifying a load, an originatinglocation identifier 1314 with a preferred date of pickup identifier1316, and a destination location identifier 1320 with a preferred dateof drop-off identifier 1322. Furthermore, field 1302 includes a truckicon 1308 that traverses along a line 1310 from start locationidentifier 1314 at one end to finish location identifier 1320 at anopposite end. Position of truck icon 1308 is provide along line 1310 ata location corresponding with the distance presently travelled by thecarrier with the cargo, as determined by GPS monitoring of the actualcarrier (and cargo). In this way, a user of the system can monitorstatus (relative position) of the cargo and carrier relative to thetotal distance being traveled between the start location and the finishlocation during the delivery.

FIG. 14 illustrates a screen shot showing customer load details in adetail menu 1402 including status of a load submitted and pending, aswell as status of carrier approval. A status indicator field 1404 showsthe status of a shipping request under review.

FIG. 15 illustrates a screen shot showing a customer new load data entryinput menu 1506 obtained by selecting a “Create New Load” identifier1504 with a mouse cursor 1502. Menu 1506 includes an explanation, or“How it works” explanation field 1508, a “What are you shipping andwhere is it going?” field 1510, a “Weight & Dimensions” field 1512, anda “Shipping & Receiving Dates” field 1514.

FIG. 16 illustrates load details including a newly created load realizedby accessing “Create New Load” field 1504 with a temporal range pop-upmenu 1603. Menu 1603 is generated by selecting “Preferred EarliestPickup Date” field 1602 within field 1514 using a mouse cursor 1601.

FIG. 17 illustrates a flowchart for depicting account manager loadinteraction flow and privileges in accordance with an exemplaryembodiment. With reference to FIG. 17, a flow of logic that is executedin various embodiments, when implementing the creation and submission ofload data is illustrated. The process can start at step 1700. After step1700, the process proceeds to step 1701 where a load is created by auser. After performing step 1701, the process proceeds to step 1702where a query is made as to whether the created load has required data(for submission to the load boards). If so, the process proceeds to step1704. If not, the process proceeds to step 1703. After step 1703, theprocess terminates. In step 1703, the load does not have required dataand cannot be posted to the board(s). In step 1705, the load board hooksare fired. After step 1706, carriers add bids to the load on the loadboard. After performing step 1706, the process proceeds to step 1707where a broker approves a carrier (from those that have added a bid tothe load). After performing step 1707, the process proceeds to step 1708where the load status changes to “waiting for pickup”. After performingstep 1708, the process proceeds to step 1709 where “waiting for pickup”hooks are fired that trigger a series of system events that aremandatory for that status of the load and operation of the system. Afterperforming step 1709, the process proceeds to step 1710 where a brokerchanges load status to “on road”. After performing step 1710, theprocess proceeds to step 1711 where the load status on the systemactually changes to “on road”. After performing step 1711, the processproceeds to step 1712 where “on road” hooks are fired. After performingstep 1712, the process proceeds to step 1713 where the load statuschanged to “load delivered”. After performing step 1713, the processproceeds to step 1714 where “load delivered” hooks are fired. Afterperforming step 1714, the load is marked “BOL received”. Afterperforming step 1715, the process proceeds to step 1716 where “BOLreceived” hooks are fired. After performing step 1716, the processproceeds to step 1717 where broker privileges are changed to “view only”status. After step 1717, the process is terminated.

As detailed in FIG. 17, the disclosed system provides for accountmanagement and accountability for brokers. First, accountrepresentatives (or brokers) cannot modify a load after it has beendelivered. Secondly, all management of load after delivery is shifted toother departments. For example, after the shift (or lock-out), anexemplary account representative will only be enabled with the abilityto view load and account information. Thirdly, only the accountingdepartment can close a load after it has been delivered. Finally, onlyan administrator can modify the load outside of the normal flow process.A normal flow process for a brokered process proceeds sequentially, asfollows: created→submitted to boards→carriers add bids→broker approvescarrier→load on road→load delivered→BOL (Bill of Lading) received→loadclosed (after billing). A normal flow process for a dispatchedcustomer's flow process proceeds sequentially, as follows:draft→submitted to rep→submitted to boards→carriers add bids→customerapproves bids→carrier signifies availability→load on road→loaddelivered→BOL received→load closed (after billing).

FIGS. 18A and 18B together illustrate a flowchart depicting a system forrating carriers having checks and balances in accordance with anexemplary embodiment. With reference to FIGS. 4A and 4B, a flow of logicthat is executed in various embodiments, when implementing a system ofchecks and balances in the process of rating carriers is illustrated.The process can start at step 1800. In step 1800, carrier data ismodified from user input or external data. After performing step 1800,the process proceeds to step 1802. In step 1801, the process can startwhen a user selects a black flag under a carrier profile. Afterperforming step 1801, the process proceeds to step 1802. In step 1802, acarrier status update starts. After performing step 1802, the processproceeds to step 1803 where a query is implemented to determine whethera carrier has common or contract authority. If the carrier does haveauthority, then the process proceeds to step 1804. If not, the processproceeds to step 1805. In step 1804, a query is implemented to determineif the carrier has cargo and auto insurance. If the carrier does havethe insurance, the process proceeds to step 1807. If not, the processproceeds to step 1805. In step 1807, a query is implemented to determineif the carrier is flagged “black”. If the carrier has been flagged“black”, the process proceeds to step 1805. If not, the process proceedsto step 1808. In step 1805, the carrier is flagged “red”. In step 1808,a query is implemented to determine if a carrier's insurance has beeninternally flagged as a high risk. If so, the process proceeds to step1809. If not, the process proceeds to step 1811. After performing step1805, the process proceeds to step 1806 where carrier bids can be added,but not approved for any load. After performing step 1808, the processproceeds to step 1809 where a carrier is flagged “yellow”. Afterperforming step 1809, the process proceeds to step 1810 where a carriersupdated data and status are saved to a database. In step 1811, a queryis implemented to determine if a carrier contract or common authority ispending. If so, the process proceeds to step 1809. If not, the processproceeds to step 1812. In step 1812, a query is implemented to determineif carrier cargo or auto insurance will expire within “X” days (X beinga determined or set number of days, such as 30 days). If so, the processproceeds to step 1809. If not, the process proceeds to step 1813. Instep 1813, a query is implemented to determine if a carrier has properattached paperwork to their profile. If so, the process proceeds to step1814. If not, the process proceeds to step 1809. In step 1814, a carrieris flagged “green”. After performing step 1814, the process proceeds tostep 1816 and to step 1810. In step 1816, the carrier bids can beapproved and they can be assigned to the load. After performing step1816, the process terminates. In step 1815, a broker determines ifcarrier status is relevant on a case-by-case basis. After performingstep 1815, the process proceeds to step 1806 and step 1816.

As detailed in FIG. 18, the disclosed system provides for carriercompliance including an inter-office black list. Carriers are colorcoded for usability: namely, green (safe/insured), yellow (elevatedrisk/close to losing insurance), and red (risky/lost insurance).Notifications are provided if a particular carrier loses their insuranceon a load (this data is pulled from both third-party systems andapplicant's own internal management system). Such notifications areshown by item 2002 (of FIG. 20) and items 2110 and 2112 (of FIG. 21).Current logic for color coding is as follows: red is the worse caseindicating no insurance; yellow is between red and green and indicatesthat insurance is soon at risk of loss; and green indicates insurance isin place and the carrier does not present a know risk. In addition, oroptionally, black can be used to indicate that a carrier has beeninternally black-flagged, and should not be considered for anydeliveries. If insurance is flagged due to an imminent lapse, a yellowdesignation is applied. If the carrier has neither common or contractauthority, then a yellow designation is used. If no cargo or autoinsurance is in place, a red designation is used. If cargo or autoinsurance is going to expire in less than 30 days, then a yellowdesignation is used. All other cases will be provided with a greendesignation. Other suitable criteria for setting a risk-based colordesignation on a carrier include using information as to whether theyhave a W-9/EIN on file with applicant, as well as whether there is anexisting contract in place with the carrier.

FIGS. 19A and 19B together illustrate a flowchart depicting logic behindselection of a temporal range in accordance with an exemplaryembodiment. The process can start at step 1900. In step 1900, a useropens a temporal modal. After step 1900, the process proceeds to step1901 where a user provides input from a mouse (or input device) at aclient. From step 1901, a user proceeds to one of steps 1902, 1906,1910, 1914, 1918, 1921, 1923, 1925, 1929, 1933, and 1936. In step 1902,the user selects “BETWEEN”. After step 1902, the process proceeds tostep 1903 where the selected type is set. After step 1903, a query ismade at step 1904 to determine if the dates are set. If the dates areset, the process proceeds to step 1905 where days between the set (orselected) dates are highlighted (inclusive). After step 1905, theprocess proceeds to step 1901. If the dates are not set, the processproceeds to step 1901. In step 1906, the user selects “BEFORE”. Afterstep 1906, the process proceeds to step 1907 where the selected type isset. After step 1907, a query is made at step 1908 to determine if thedates are set. If the dates are set, the process proceeds to step 1909where days before the set (or selected) end date are highlighted(inclusive). After step 1909, the process proceeds to step 1901. If thedates are not set, the process proceeds to step 1901. In step 1910, theuser selects “AFTER”. After step 1910, the process proceeds to step 1911where the selected type is set. After step 1911, a query is made at step1912 to determine if the dates are set. If the dates are set, theprocess proceeds to step 1913 where days after the set (or selected)start date are highlighted (inclusive). After step 1913, the processproceeds to step 1901. If the dates are not set, the process proceeds tostep 1901.

In step 1914, the user selects “AT”. After step 1914, the processproceeds to step 1915 where the selected type is set. After step 1915, aquery is made at step 1916 to determine if the dates are set. If thedates are set, the process proceeds to step 1917 where only the startdate is highlighted (inclusive). After step 1917, the process proceedsto step 1901. If the dates are not set, the process proceeds to step1901.

In step 1918, the user selects “N/A” (not available). After step 1918,the process proceeds to step 1919 where the selected type is set. Afterstep 1919, the process proceeds to step 1920 where all highlights areremoved. After step 1920, the process proceeds to step 1901.

In step 1921, the user selects “USE TIME”. After step 1921, the processproceeds to step 1922 where the display of time input is toggled. Afterstep 1922, the process proceeds to step 1901.

In step 1923, the user selects a time input. After step 1923, theprocess proceeds to step 1924 where the user inputs time. After step1924, the process proceeds to step 1901.

In step 1925, the user selects or clicks on a date. After step 1925, theprocess proceeds to step 1926 where type is set to “AT”. After step1926, the process proceeds to step 1927 where start is set to the dateselected. After step 1927, the process proceeds to step 1928 where onlythe start date is highlighted. After step 1928, the process proceeds tostep 1901.

In step 1929, the user clicks and drags between two dates. After step1929, the process proceeds to step 1930 where the type is set to“BETWEEN”. After step 1930, the process proceeds to step 1931 where auser sets start and end to first and last dates selected. After step1931, the process proceeds to step 1932 where days between selecteddates are highlighted. After step 1932, the process proceeds to step1901.

In step 1933, the user selects “OK”. After step 1933, the processproceeds to step 1934 where a temporal timeframe string is prepared.After step 1934, the process proceeds to step 1935 where the timeframestring is passed to a parent object. After step 1935, the processproceeds to step 1937 where the modal is closed.

In step 1936, the user selects “CANCEL”. After step 1936, the processproceeds to step 1937 where the modal is closed.

FIG. 20 illustrates a screen shot for a carrier profile for “FDCEnterprises LLC” to access through one or more interfaces the featuresand functionality of FIG. 1 in accordance with an exemplary embodiment.More particularly, the carrier profile of FIG. 20 shows an insurance“Grade” field 2004 with a corresponding rating value of “B-” in field206.

FIG. 21 illustrates an account manager/broker screen shot for a brokerdesignated in field 2102 and depicting a load profile with quotesattached to a load with carrier ratings. More particularly, a “Rates”field 2104 identifies individual shippers “XYZ Trucking” and “EFDTrucking” via respective open quote fields 2106 and 2108.

FIG. 22 illustrates an account manager/broker screen shot depicting amenu for interacting with a carrier rate on a load menu. Multiple quotesfrom unique sources (indicated by carriers 2106 and 2108) are shown, asfurther previously depicted by reference numeral 408 of FIG. 4B. Moreparticularly, a note text field 2202 enables a user to input commentsrelating to that carrier bid and a selectable “Approve” button 2204 and“Decline” button 2206 enable a user to indicate approval or decline of aparticular carrier bid.

FIG. 23 illustrates a broker-side screen shot depicting a customerprofile. More particularly, an “Account” type display field 2302 isshown above a “Loads” type display field 2308. Field 2302 includes an“Account Type” field category 2304 with a presently displayed “FullyBrokered” field value, or visual indicia that is further represented byone of a series of vehicle representations by vehicle icon 2305. Field2304 correlates with item 406 in FIG. 4A.

FIG. 24 illustrates a broker-side screen shot depicting a brand newload. A cursor 2401 is “moused-over” a preferred equipment “Unspecified”field 2402 which generates pop-up menu 2502 in FIG. 25, below.

FIG. 25 illustrates a screen shot depicting the selection of equipmentfor the new load depicted in FIG. 25. More particularly, pop-up menu2502 depicts a list of unique trailer types that can be selected by auser via menu 2502. The list of unique trailer types is queried from adatabase of industry standard trailer types and transportation methods(including intermodal). A search box field 2504 is also provided forinputting and searching the database for a specific type of trailer ortransportation method.

FIG. 26 illustrates a screen shot depicting a new load and adding a newline item to a customer's invoice. More particularly, a pop-up menu 2602is used to add a line item to a customer invoice based onindustry-specific needs. The data input via menu 2602 is automaticallyprovided as input into an accounting management program, such as QuickBooks™.

FIG. 27 illustrates a screen shot depicting realization of the line itemadded to the customer's invoice of FIG. 26. More particularly,“Tarp/Tailgate” field 2702 has been added along with a value field entry2704 of $150.

FIG. 28 illustrates a screen shot depicting the ability to add a shipperand a receiver for a designated city and state. A “Route” data entryfield 2802 is provided with a “Shipper” data entry field 2804 and a“Receiver” data entry field 2806. Shipper waypoint location and loadinformation is entered by a user into field 2804. Receiver waypointlocation and load information is entered by a user into field 2806.

FIG. 29 illustrates a screen shot depicting a pop-up menu 2902 whileselecting a temporal date range. More particularly, a “Between” daterange selection feature 2904 has been selected to enable a singletactile input gesture (such as click-and-drag operation) for selecting arange of dates.

FIG. 30 illustrates a screen shot depicting the pop-up menu 2902 of FIG.29 while selecting a temporal time range. A selected date range is shownfor a “Shipper” as subsequently depicted in FIG. 32. Encircled “5”indicates the present date.

FIG. 31 illustrates a screen shot depicting the pop-up menu 2902 ofFIGS. 29 and 30 while selecting a temporal “after” time range 3104 shownfor a “Receiver” as subsequently depicted in FIG. 32. More particularly,all dates after (and including) Feb. 19, 2014 are selected.

FIG. 32 illustrates a screen shot depicting a realized selected temporalrange implemented via actions depicted in FIGS. 29-31. A selected daterange 3202 and 3204 is shown for both the “Shipper” and the “Receiver”,respectively. Additionally, a “Weight” data entry field 3206 hasreceived an input of “3T” (lb.).

FIG. 33 illustrates a screen shot depicting automatically convertedunits of weight for a specific cargo over that entered in the screenshot of FIG. 32. “Weight” data entry field 3206 has been automaticallyconverted in units (from tons) into pounds (lb.). Additionally,automatic conversions of units, such as English and metric unit measuresare implemented via such system and feature. Finally, a cursor 3201 is“moused-over” “POST TO LOAD BOARD” button which triggers posting of theinput information to the load board.

FIG. 34 illustrates a screen shot depicting a load status change “PUT ONHOLD” designated by item 3402 resulting from selection of a “POST TOLOAD BOARDS” field 3203 (in FIG. 33). Further details of the load statuschange are provided in FIG. 17, above.

FIG. 35 illustrates a screen shot depicting the adding of a carrierquote where permissions change the rate and “XYZ TRUCKING” is added. Anotifications message window 3502 is shown after selecting“Notifications” selection item 3504.

FIG. 36 illustrates a screen shot depicting the addition of a secondcarrier quote indicated by reference item 3602 to provide for multiplequotes. Item 3602 represents a rate of $3,500 for “XYZ Transport” whichcomprises an “Open Quote”.

FIG. 37 illustrates a screen shot depicting a carrier quote menu. Moreparticularly, a cursor 3701 is “moused-over” a “No Equipment Specified”menu selection item 3702 which causes pop-up menu 3802 to be enabled inFIG. 38.

FIG. 38 illustrates a screen shot depicting a pop-up menu for addingcarrier quote equipment. More particularly, pop-up menu 3802 depicts alist of unique trailer types that can be selected by a user via menu3802. The list of unique trailer types is queried from a database ofindustry standard trailer types and transportation methods (includingintermodal). A search box field is also provided for inputting andsearching the database for a specific type of trailer or transportationmethod.

FIG. 39 illustrates a screen shot depicting realized changes of carrierquote equipment type from actions taken by a user depicted previously inFIG. 37 and FIG. 38.

FIG. 40 illustrates a screen shot depicting the addition of a note to acarrier. More particularly, “XYZ Trucking” text input field 4002includes a note input field 4004 in which indicia, or text 4006 has beeninput by a user.

FIG. 41 illustrates a screen shot depicting realization of the addednote input in FIG. 40.

FIG. 42 illustrates a screen shot depicting realizing equipment changesfor the listed carrier with the added note and approval of “XYZTRUCKING”. A cursor 4201 is “moused-over” an “Approved” selectionbutton, when clicked, causes the identified carrier to be approved onthe load. A “Decline” selection button 4204 is also provided fordeclining that carrier.

FIG. 43 illustrates a screen shot depicting realized changes forapproved carrier “XYZ TRUCKING” resulting from selection of “Approved”selection button 4204 (in FIG. 42). In addition, a “Carrier” field 4302now shows “XYZ Trucking”. An “Equipment” field 4304 shows “Cargo Van”. Acarrier pay field 4306 shows “$3,900”.

FIG. 44 illustrates a screen shot depicting creation of carrier ratepaperwork. By selecting a lock icon 4308 above carrier pay field 4306using cursory 4401, it creates paperwork as shown below with referenceto FIGS. 45 and 46.

FIG. 45 illustrates a screen shot depicting a pop-up screen 4502 thatprovides a secondary check to a user indicating that this operation isdesired by the user. A user is presented with an “OK” selection button4504 and a “Cancel” selection button 4506 for respectively launching orcancelling the “lock” to respective system data and limits the abilityfor values to be changed, such as permission-locking user access to onlyadministrative or broker level personnel (other users will be preventedfrom unlocking the data and making changes).

FIG. 46 illustrates a screen shot depicting realization of carrier rateconfirmation paperwork which is triggered as a result of selecting “OK”button 4504 in FIG. 45. As a result, “Paperwork” menu portion 4602 isshown having an added “Carrier Rate Confirmation” item 4604. A carrierpay rate item 4606 is also provided as “$3,900”.

FIG. 47 illustrates a screen shot depicting realization of customer rateconfirmation paperwork. A cursor 4701 is shown selecting item 4606which, in a locked state, generates a “disabled feature” icon 4702.

FIG. 48 illustrates a screen shot depicting selection of change of loadstatus to “IN TRANSIT”. A cursor 4801 is shown selecting “MOVE TO INTRANSIT” button 4802 which causes a screen display change representedbelow in FIG. 49.

FIG. 49 illustrates a screen shot depicting realization of selection ofthe changed load status in FIG. 48. A “MOVE TO DELIVERED” button 4902 isthen provided for selection by a user.

FIG. 50 illustrates a screen shot depicting added notes to a load withcarrier permissions to view. A cursor 5001 is provided (hovers) over acarrier note permissions icon 5002. A tool tips, or pop-up box 5004 isgenerated to display the current carrier note permissions status.

FIG. 51 illustrates a screen shot depicting that selection is being toenable viewing by the carrier of note text.

In compliance with the statute, the subject matter disclosed herein hasbeen described in language more or less specific as to structural andmethodical features. It is to be understood, however, that the claimsare not limited to the specific features shown and described, since themeans herein disclosed comprise example embodiments. The claims are thusto be afforded full scope as literally worded, and to be appropriatelyinterpreted in accordance with the doctrine of equivalents.

The invention claimed is:
 1. An apparatus for managing transportation of freight, comprising: a server; a plurality of carrier vehicles each configured to haul a load; and a plurality of clients each associated with one of the plurality of carrier vehicles and each client having a user interface; and a processor designed to process instructions to provide date and time selection to the client from the server to enable temporal scheduling of a load to be transported for a prospective transportation industry customer; the server having a non-transitory machine readable memory having stored therein computer instructions programmed to cause the processor to: store user information and instructions in the memory at the host server; access the memory at the server to retrieve the user information and instructions and execute the instructions to perform steps to: present from the server to the plurality of clients at the user interface one or more of a selectable date range and a time range for which the user provides a temporal-based requirement for picking up a load for a customer; enable selection of one or more of a date range and a time range at the user interface of each of the plurality of clients; receive a selected one or more of the date range and the time range at the server from a user at one of the clients; store the received and selected one or more of the date range and the time range into a database of the server; associate the stored one or more of the date range and the time range with a waypoint indicative of a cargo delivery destination desired by the customer; associate the waypoint to a load; associate the load to the customer; present the load, the waypoint, the date range and the time range to at least one shipper via the user interface at each of the plurality of clients each having equipment configured to move the load; receive via the user interface at the server from a client a quote from one of the at least one shipper to move the load at the waypoint within the date range and the time range; generate at the server for delivery to a display at a client visible display notes characterizing status of carrier permissions based on one or more conditions being met by the carrier to a user having carrier note permissions to view the status of the carrier permissions; at the server, from a remote client, accept the quote from the one shipper to move the load; at the server, permission-locking user access on an electronic bill of lading comprising the accepted quote to only administrative or authorized broker level personnel, the locked user access preventing the one shipper after booking and at least one of: a broker shipper, a customer, a receiver, and an insurance provider from modifying the electronic bill, to secure data on the electronic bill of lading after the load is delivered and the electronic bill of lading is generated; shifting management of load delivery upon permission-locking user access to a uniquely different department having uniquely different account representatives than the broker; from the server, simultaneously generating and delivering by electronic transmission the permission-locked electronic bill of lading including the accepted quote to the one shipper to acknowledge and initiate resource allocation of the equipment by directing movement of one of the plurality of carrier vehicles to acquire and move the load at the waypoint for delivery to the prospective transportation industry customer; delivering the load from the waypoint to the customer; at the server, changing status of the load to delivered and rendering notes to the delivered load associated with the delivered and permission-locked electronic bill of lading selectively viewable by the carrier when granted permission by administrator or broker level personnel having access permission; and generating a final delivered and permission-locked electronic bill of lading received after delivering the load to the customer using one of the uniquely different account representatives having permission-locked data presentable to the shipper after delivering the load.
 2. The apparatus of claim 1, wherein the user is a load scheduling participant.
 3. The apparatus of claim 2, wherein the load scheduling participant is a customer.
 4. The apparatus of claim 2, wherein the load scheduling participant is a broker, and wherein presenting comprises presenting from the server to the broker at the user interface of the client one or more of a selectable date range and a time range for which the broker provides a temporal-based requirement for picking up a customer load.
 5. The apparatus of claim 4, wherein the one or more of a selectable date range and the time range comprises a temporal range graphical user interface selection menu.
 6. The apparatus of claim 1, wherein the load scheduling participant is a customer, and wherein presenting comprises presenting from the server to the customer at the user interface of the client one or more of a selectable date range and a time range for which the customer provides a temporal-based requirement for picking up a customer load.
 7. The apparatus of claim 6, wherein the one or more of a selectable date range and the time range comprises a temporal range graphical user interface selection menu.
 8. The apparatus of claim 1, wherein enabling selection of one or more of a date range and a time range at a user interface of the client comprises using a single tactile input gesture to capture a temporal range.
 9. The device of claim 1, wherein the server having further instructions stored in the memory to cause the processor to store indicia about the at least one shipper indicative of at least one of: a) insurance status; b) carrier compliance; and c) common and contract authority.
 10. The device of claim 1, wherein the server having further instructions stored in the memory to cause the processor to parse in one of a plurality of ways the selected date and time range and post the parsed selected date and time range to an industry standard load board.
 11. The device of claim 1, wherein the server having further instructions stored in the memory to cause the processor to authenticate a user at the user interface.
 12. The device of claim 1, wherein the server having further instructions stored in the memory to cause the processor to categorize the type of user, and generate one of a plurality of unique user interfaces for the categorized type of user.
 13. The device of claim 1, further comprising a fleet of vehicles associated with one shipper, one of the fleet of vehicles rendered operative to acquire and move the load at the waypoint for delivery to the prospective transportation industry customer.
 14. The device of claim 1, wherein shifting management of load delivery to a uniquely different department comprises enabling exclusively an accounting department with the ability to close a load after the load has been delivered.
 15. The device of claim 1, further comprising exclusively enabling an administrator with an ability to modify the load outside of a normal flow process.
 16. The device of claim 1, wherein the broker is only enabled with the ability to view load and account information after locking out the broker. 